Purpose: This program will update the TacOps program verson 0.0.0 to version 0.0.1.
Scope: All users of TacOps version 0.0.0 should install this update. This update will not spoil any version 0.0.0 saved games or version 0.0.0 EMail games in progress. However, email games in progress should not be continued until both players have updated their copy of TacOps to version 0.0.1.
Caution: Do not update files on your factory provided disks. These are your emergency backups and they should not be altered. For safety, update only the TacOps application file that you have already installed on your hard drive.
=================================
Instructions:
(1) Before running the update installer program, restart your Macintosh while holding down the shift key. This will prevent most INITs and Extensions from loading and potentially interfering with the update process.
(2) Do not run any program in your Mac's background while installing this update.
(3) Turn off or disable any virus checking program before attempting to update TacOps. The update installer changes code and other resources inside your TacOps program. If you have a virus checking program running in the background it may wrongly interpret the update process as an attempted infection.
(4) Copy the folder named "TacOps Update 0.0.1" onto your hard disk at the same folder level as the TacOps game file. As a precaution, also copy the folder named "TacOps Update 0.0.1" to a backup floppy disk. As a precaution, also copy the TacOps game application file version 0.0.0 to a back up floppy.
(5) Open the folder named "TacOps Update 0.0.1".
(6) Doubleclick on the file named "TacOps Update Installer".
(7) When told to do so by the installer program, select the TacOps application file to be updated.
(8) If the installer successfully completes the update, the installer program will automatically quit.
(9) If a problem occurs, the program will show you an error message. If you see any error message or if the installation is interrupted in any manner (such as a power failure), do not attempt to repeat the update twice on the same copy of your TacOps file - the file might have been corrupted by whatever caused the error message. Instead, use your backup floppy or your factory provided disks to place a fresh copy of TacOps version 0.0.0 on your hard disk and then repeat your attempt to install the update.
(10) After successful installation of the update, the version number in your TacOps program's Get Info box should show "version 0.0.1". The version number of a Macintosh program may be viewed by selecting the program's icon and then selecting the "Get Info" menu item in the Macintosh desktop menu named "File".
(11) After successful installation, remove the folder named "TacOps Update 0.0.1" from your hard disk. Its forgotten presence on your hard disk could conflict with the installation of future updates.
(12) After successful installation, shut down and restart your computer.
=================================
Changes:
(1) OPFOR Unmanned Aerial Vehicle was showing the green symbol of a US Kiowa helicopter.
(2) The "Set DF TRP" button in the Unit Orders Window did not dim when user opened the window for an Unmanned Aerial Vehicle.
(3) Unmanned Aerial Vehicle was showing strange numbers (to include very large negative numbers) in the max range box under the range scroll bar in the Unit Orders Window - should have been showing 0 for a max range since it has no weapons.
(4) Fixed following cosmetic bug: "Select the Options menu: Change Artillery Support menu item, if you "UNUSE" the second howitzer (SLOT 2) and use instead an MLRS (SLOT 3) the MLRS won't appear on the artillery support menu in the game." Problem was caused by user leaving empty slots between arty units. Added code to check for this conditon and if found to close up the new arty list so as to skip any empty slots.
(5) Fixed following cosmetic bug: "Select the Options menu: Change Artillery Support menu item, if one changes the 2nd howitzer (SLOT 2) into an MLRS and back again [into a howitzer] (the howitzer can then only fire 7 ICM's and no HE or smoke). User does not have access to the data entry blocks for HE or SMOKE for that slot anymore unless he closes anad reopens the change dialog."
(6) A number of users complained about the Game Status Report being automatically shown after they had selected Quit or New Game. They felt that once a user had indicated that he wanted to quit a game then the program ought to just quit. I removed the offending feature.
(7) The firing info message incorrectly substitued the word "entrenchment" for the type of unit being fired on during direct fire at units inside entrenchments even though the target units were plainly visible to the user.
(8) The top turret machine gun on M1 tanks, LAVs, and probably some other vehicles was incorrectly identified as an "M60" machine gun - they are now more often M240s. The US infantry machine gun was also identified as an M60 and the USMC is about to change to a different weapon. To eliminate these inaccuracies, we changed the names to "7.62mm machine gun". The combat resolution tables were not changed so there is no impact on game logic/play.
(9) The "Go To Unit" menu item would wrongfully open the orders window of off map APCs carrying infantry.
(10) The Ammo Reports were not disabling conflicting command key sequences.
(11) The Ammo Reports should have only been reporting the ammo status of on map units.
(12) Made the appearance and functioning of the reports accessed throught the Reports menu more consistent with one another.
(13) For user convenience, increased the use of Command W keystroke for dismissing windows and added it as a menu item in the file menu.
(14) A number of the reports in the Reports menu were failing to disable conflicting command key sequences before drawing to the screen.
(15) •Fixed bug in game play. Smoke on high ground was not consistently blocking ordinary line of sight. The bug was largely insignificant in games in which both sides possessed thermal sights. Bug was introduced by the compiler global optimizer. When the optimizer was disabled in the function that builds the line of sight block bitmaps, the bug disappeared.
(16) The entrenchment delayed orders button was being shown in the unit orders window even when the unit was not over an entrenchment symbol. This wrongly suggested that units could entrench anywhere. This button is now hidden when a unit can not in fact entrench.
